PreviousNextTracker indexSee it online !

(20/34) 27 - windows. .txt file association.

Although I like jedit,
I've unloaded it from my windows machine.

Why?

For some reason you insist on associating
.txt files
with jedit, and don't provide an option to remove it.


I choose not to use jedit for text files (too long to
load).


Very nice product though.

regards DaveP



Submitted dpawson - 2004-10-13 11:21:51 Assigned
Priority 5 Labels
Status open Group None
Resolution None

Comments

2004-10-13 21:47:34
russelldad

Logged In: YES
user_id=1113035

Note: jedit-users@lists.sourceforge.net is a great mailing
list for help with jEdit.

Opening jEdit quickly
If you add -background -reuseview to the command that opens
jEdit, it will only be "slow" to open the first time you
open it after rebooting. you can then close jEdit. The next
time you open it, jEdit will open quickly (almost as fast as
notepad.exe)

Here is an example of the command to open jEdit with those
arguments.

D:\devtools\java\j2sdk1.4.1_03\bin\javaw.exe -jar
"D:\devtools\jEdit\jedit.jar" -background -reuseview

Reassociating Files
That said, you should be able to change the file assiciation
of .txt files by right clicking on a .txt file, selecting
Choose Program,
and making sure the "Always use this program to open these
files" is checked.

Then select "notepad" or the .txt editor of your choice.

2004-10-15 14:07:53
orutherfurd

Logged In: YES
user_id=265596

DaveP,

As a workaround for the file-association problem, you can
try removing:

HKEY_CLASSES_ROOT\\\*\Shell\Open with jEdit

I don't have a good answer for how or why the file
associations are being hijacked, but a few others have
reported it, too. I'm sure it doesn't help to say that I
don't see it on my machine -- but I don't.

If I can't figure out why this is happening, it maybe be
better to not create the context menu entry for future
versions -- until a better solution can be found.

2006-03-21 19:33:42
bemace

- **labels**: 102668 -->

2007-04-18 20:14:53
rschwenn

Logged In: YES
user_id=1486645
Originator: NO

Has anyone ever seen the registry entries, that seem to cause the hijacking?